Summary

This PR adds a custom logs panel instead of using the builtin Grafana logs panel, giving us total control over the it. The builtin Grafana panel does a lot for you, but provides no customization if you want to do things differently (even minor things like custom styling seem to be impossible). With this custom rewrite we've already been able to reduce several pain points and difficulties we ran into going the builtin route.

Though this is only the first pass, it contains all the necessary functionality to be usable, including:

• Rendering all the logs in a clean and easily readable format
• Unfurling a log and seeing the full contents
• Automatically linking from a trace in KalDB to the associated datasource (such as Zipkin)

And while it's not necessary functionality, we were able to also virtualize the logs panel (although there is a bug in it, see #45)

That said, there are some features missing from this that we'll be adding in later. Things like:

• Pagination
• Adding a new column to the table to render just that field in the column
• Adding a raw JSON view
• Allowing for some more customization (read: not hardcoding as many things)

Demo

Due to this rewrite being so extensive, it's difficult to demo all the functionality in a succinct way. It's recommended you pull this and try it out for yourself.

Performance

There was a decent performance boost from this rewrite. We've reduced the number of DOM elements by over half (previous was ~25k elements, current is ~11.5k elements) and have improved our Lighthouse Score (an imperfect metric, but a readily available one). I've attached the old and new Lighthouse Score below:

Old:

New:

Resolves #36

Requirements (place an x in each [ ])

• I've read and understood the Contributing Guidelines and have done my best effort to follow them.
• I've read and agree to the Code of Conduct.

The following point can be removed after setting up CI (such as Travis) with coverage reports (such as Codecov)

• I've written tests to cover the new code and functionality included in this PR.

The following point can be removed after setting up a CLA reporting tool such as cla-assistant.io

• I've read, agree to, and signed the Contributor License Agreement (CLA).